Release 10.1A: OpenEdge Deployment:
Managing 4GL Applications

Maintaining the progress.ini file

The progress.ini file specifies environment variable settings for the Windows environment. It contains sections and settings for the following types of options:

Options required by OpenEdge.
Options required by OpenEdge tools (such as the Procedure Editor and the Report Builder).
User-defined options.
Environment variables.

Figure 4–2 shows excerpts from a sample progress.ini file.

[Startup] V6Display=no ;ImmediateDisplay=yes ;MultitaskingInterval=100 DefaultFont=MS Sans Serif, size=8 DefaultFixedFont=Courier New, size=8 DLC=C:\Progress\OpenEdge Use-3D-Size=Yes PROPATH=.,C:\Progress\OpenEdge\C:\Progress\OpenEdge\bin UseSourceEditor=yes EditorConfigPath=C:\OpenEdge\WRK\proedit . . . [WinChar Startup] DLC=C:\Progress\OpenEdge PROCFG=C:\DLC\PROGRESS.CFG PROMSGS=C:\DLC\PROLANG\PROMSGS.GER PROPATH=.,C:\DLC V6Keys=No V6FKeys=No . . .

Figure 4–2: Sample Progress initialization file in Windows

When installed, the progress.ini file contains the following sections:

Startup section.
Colors section.
Default Window section.
Fonts section.
WinChar Startup section.
WinChar Colors section.
WinChar Default Window section.
WinChar Keys section.

The progress.ini file can also contain the following optional sections:

"Debug-Init section" section.
"Debug-Macros section" section.
"Debug-Buttons section" section.
"Keys section" section.
"Keymap section" section.

You can edit the progress.ini file to customize environments at different sites. The progress.ini file is located in the install-dir\bin directory, by default.

The following sections describe each of these progress.ini file sections.

Startup section

The Startup section of the progress.ini file contains options that specify the following environment characteristics for graphical user interface clients:

Display attributes and multi-tasking capabilities.
Default fonts used for displaying and printing alphanumeric data.

The Startup section also contains OpenEdge environment variables that you can set for use with graphical user interface clients. See Table 4–5 in the "Specifying environment variables" section for a list of environment variables you can set in the Startup section.

The Startup section contains the following options:

AlignFrameTitles

AlignFrameTitles=n

Lets you specify the alignment of frame titles in a graphical user interface. Valid settings include the following: 0 (left justified), 1 (centered), and 2 (right justified). The default is centered.

ButtonImageBorderMode

ButtonImageBorderMode=n

Use this setting if you want to change the default behavior of how OpenEdge draws borders on buttons with images. The border drawing behavior for image buttons depends on two factors:

The type of image button—single-image or dual-image. Dual-image buttons use two images (an “up” image and a “down” image). Single-image buttons use one image (an “up” image which is shifted slightly to mimic a “down” appearance for the button).
The presence of a manifest file. For more details on manifest files, see the "The Windows manifest file" section.

The default behavior is:

For single-image buttons, OpenEdge creates a Windows XP-style border (rounded corners, no 3D shadow) when using the manifest file. It draws a Windows classic-style border (angular corners with 3D shadow) when not using the manifest file.
For dual-image buttons, OpenEdge does not draw a border for the button, regardless of whether there is a manifest file. (Note that this is the default behavior. You can change the value of ButtonImageBorderMode to 2 if you want OpenEdge to draw a border for dual-image buttons.)

Table 4–1 describes OpenEdge’s border drawing behavior, based on the value of the ButtonImageBorderMode setting. If you want to keep the default behavior, you do not need to add this setting to your progress.ini file.

Table 4–1: Image button border drawing behavior

Type of image button	ButtonImageBorderMode value of n
	1 (default)	2	3
Single-image button with manifest file	Adds an XP-style border to the button.	Adds an XP-style border to the button.	Adds a classic-style border to the button.
Single-image button without manifest file	Adds a classic-style border to the button.	Adds a classic-style border to the button.	Adds a classic-style border to the button.
Dual-image button with manifest file	No border added.	Adds an XP-style border to the button.	No border added.
Dual-image button without manifest file	No border added.	Adds a classic-style border to the button.	No border added.

Note that ButtonImageBorderMode affects clients running on XP with a manifest file and clients running on non-XP systems (or XP without a manifest file). The same setting is required for all clients.

CarefulPaint

CarefulPaint={ YES | NO }

Lets you set the accuracy with which OpenEdge repaints overlapping 3D widgets and frames. Set to YES for OpenEdge to repaint overlapping 3D widgets and frames slowly and carefully. Set to NO for OpenEdge to repaint overlapping 3D widgets and frames quickly (which might reduce the quality of the graphic). The default value is YES.

This option applies only when UseNative3D=NO.

ClientTimeOut

ClientTimeOut=n

Lets you specify the number of minutes a client session can remain inactive before the server disconnects the session.

The server process determines whether a client has been inactive for a specified period of time, and if so, the server disconnects the client and backs out any related active transactions.

DefaultFixedFont

DefaultFixedFont=typeface, [ size point-size, keyword, ... ], [ script=scriptname ]

Lets you specify the default fixed display font.

typeface

A valid typeface name, such as Times or Courier.

point-size

The size of the font, in points. If you omit the point size, OpenEdge uses the default point size as defined by the typeface.

keyword

You can specify the following keywords: bold, italic, underline, or strikeout.

scriptname

By default, OpenEdge uses the script (character set) of the Windows FixedSys font for all fonts specified in the environment. If you select a different script when editing a font using the font common dialog, OpenEdge writes the specified script name to the font entry.

DefaultFont

DefaultFont=typeface, [ size point-size, keyword, ... ], [ script=scriptname ]

Lets you specify the default display font.

typeface

A valid typeface name, such as Times or Courier.

point-size

The size of the font, in points. If you omit the point size, OpenEdge uses the default point size as defined by the typeface.

keyword

You can specify the following keywords: bold, italic, underline, or strikeout.

scriptname

By default, OpenEdge uses the script (character set) of the Windows FixedSys font for all fonts specified in the environment. If you select a different script when editing a font using the font common dialog, OpenEdge writes the specified script name to the font entry.

DefaultV6UpdateFont

DefaultV6UpdateFont=typeface, [ size point-size, keyword, ... ], [ script=scriptname ]

Lets you specify the Version 6 update font.

typeface

A valid typeface name, such as Times or Courier.

point-size

The size of the font, in points. If you omit the point size, OpenEdge uses the default point size as defined by the typeface.

keyword

You can specify the following keywords: bold, italic, underline, or strikeout.

scriptname

By default, OpenEdge uses the script (character set) of the Windows FixedSys font for all fonts specified in the environment. If you select a different script when editing a font using the font common dialog, OpenEdge writes the specified script name to the font entry.

When V6Display=YES, the font specified by the DefaultV6UpdateFont setting is used when a fill-in is in update mode. The default value for DefaultV6UpdateFont is a version of the system default fixed font with underlines (fixedsys, underline).

The DefaultFixedFont and the DefaultV6UpdateFont should be the same base font. If you change them, make sure that the font is fixed and that the DefaultV6UpdateFont has the underline attribute. OpenEdge does not automatically add the underline attribute to the DefaultV6UpdateFont setting.

EndMsgTitle
EndMsgText

EndMsgTitle=title-text EndMsgText=message-text

Lets you specify the title and text for the Windows shutdown message box.

When Windows shuts down, a dialog box prompts the user to verify the shutdown. If the user answers YES, OpenEdge closes and the Windows Exit procedure continues. If the user answers NO, the Windows Exit procedure terminates and Windows remains active.

EndMsgTitle can be up to 80 characters long. Its default value is “OpenEdge.” EndMsgText can be up to 80 characters long. Its default value is “Windows is exiting. Is this OK?”.

FrameSpacing

FrameSpacing=n

Lets you specify how the OpenEdge layout processor spaces frames.

Setting the value to -1 places the frame at the next character unit boundary. Setting the value to 0 places frames one half of a character unit apart. Setting the value greater than 0 spaces the frames by the specified number of pixels.

ImmediateDisplay

ImmediateDisplay={ YES | NO }

Lets you redisplay the screen at predefined intervals.

If you do not set this option, some Version 6 applications will not draw the screen correctly. Set this option for applications with existing code that you do not want to modify. The default setting is NO.

You can also use the IMMEDIATE-DISPLAY attribute with the SESSION system handle to surround the offending code. This is the preferred technique.

For more information about the IMMEDIATE-DISPLAY attribute and the SESSION system handle, see OpenEdge Development: Progress 4GL Reference .

Keep3DfillinBorder

Keep3DfillinBorder={ YES | NO }

Set to YES to display a disabled fill-in field with a border. Set to NO to display a disabled fill-in field without a border. The default value is NO.

MultitaskingInterval

MultitaskingInterval=n

Lets you specify how the OpenEdge session interacts with a Windows cooperative multi-tasking environment. Its value determines how often OpenEdge filters events or messages between itself and other Windows applications. As OpenEdge filters these events more often, it executes procedures less efficiently but allows other Windows applications more opportunity to execute. Adjusting the internal event filter is particularly useful during background processing, such as report generation.

To maximize performance during batch-mode processing, set the value to 9999 (the maximum value allowed). If you want to run another application while you run OpenEdge in batch mode, set the value to 1000. If you set the value to 0 (the default), the internal loop never executes. Although this results in high performance, interoperability with other Windows applications is poor. The lower the number, the more often the loop executes, resulting in better interoperability. Set this option for applications with existing code that you do not want to modify.

You can also use the MULTITASKING-INTERVAL attribute with the SESSION system handle to control how OpenEdge interacts with Windows cooperative multi-tasking by surrounding long 4GL processing loops with this attribute.

See OpenEdge Development: Progress 4GL Reference for more information about the MULTITASKING-INTERVAL attribute and the SESSION system handle.

NoSplash

NoSplash={ YES | NO }

Set to YES to turn off display of the splash screen. By default, the OpenEdge GUI client and the WebClient display a splash screen during startup. The screen, which is a blue rectangle with the words “Powered by Progress Software,” disappears when the OpenEdge application starts.

Opsys

Opsys=character-string

Lets you specify the value used by the OPSYS preprocessor directive or the value returned by the OPSYS function. Valid settings include any character string.

PopupAppOverridesSys

PopupAppOverridesSys={ YES | NO }

Set to YES to display the system-default pop-up menu only if a user-defined pop-up menu is not available. Set to NO to display the system-default pop-up menu regardless of a user-defined pop-up menu. If a user-defined pop-up menu is available, it is displayed after the system pop-up menu is closed. The default value is YES.

Note: The system-default pop-up menu is displayed when you click the right mouse button on a fill-in field or an editor widget and a user-defined pop-up menu is not available.

PopupNoSysDefault

PopupNoSysDefault={ YES | NO }

Set to YES to suppress the system-default pop-up menu. Only the user-defined pop-up menu is displayed. The default value is NO.

Note: The system-default pop-up menu is displayed when you click the right mouse button on a fill-in field or an editor widget and a user-defined pop-up menu is not available.

PopupOnMouseDown

PopupOnMouseDown={ YES | NO }

Set to YES to display a pop-up menu when the right mouse button is depressed. Set to NO to display a pop-up menu when the right mouse button is released. The default value is NO.

Note: This option applies only to pop-up menus that are displayed with the right mouse button (that is, MENU-MOUSE = 3). Menus that are displayed with the left or middle mouse button are always displayed when the buttons are depressed.

PrinterFont

PrinterFont=typeface, [ size=screen-point-size ]

Lets you specify the printer fonts OpenEdge uses with the OUTPUT TO PRINTER statement.

PrinterFontn

PrinterFontn=typeface, [ size=screen-point-size ]

Lets you specify the printer font OpenEdge uses with the OUTPUT TO LPTn statement.

UseClipChildren

UseClipChildren={ YES | NO }

This option is set to YES by default. It works with the Windows manifest file in drawing buttons. For more information on the manifest file, see the "The Windows manifest file" section.

Caution: Do not change the default setting of the UseClipChildren option until you first talk with a Progress Software Technical Support representative.

UseNative3D

UseNative3D={ YES | NO }

This option is set to YES by default. It specifies to use Windows 3D drawing capabilities.

Set this option to NO to use OpenEdge’s 3D drawing capabilities instead. If you set the UseNative3D option to NO, you must also remove the prowin32.exe.manifest file from your installation-path\bin\ directory. If you set this option to NO and you do not remove the manifest file, you will see inconsistencies in the appearance of your user interface.

UseSourceEditor

UseSourceEditor={ YES | NO }

Set to YES if you want to use the Source Editor (Slick Edit). Set to NO if you want to use Rich Edit editor. Both editors are Unicode-enabled.

Use-3D-Size

Use-3D-Size={ YES | NO }

Lets you specify how OpenEdge calculates the height of a character unit.

If you set the value to YES, OpenEdge uses the height of a three-dimensional fill-in. If you set the value to NO, OpenEdge uses the height of a non-three-dimensional fill-in. The default setting is YES.

V6Display

V6Display={ YES | NO }

Lets you specify Progress Version 6 behavior.

When you compile a procedure in Windows, OpenEdge compiles the borders and fonts associated with user interface widgets into the screen layout by default. As a result, you might encounter compilation problems when you try to run a Version 6 application in Progress Version 7 for Windows. There might not be enough space on the display to accommodate the borders and default fonts that are automatically associated with user interface widgets of the Version 6 application.

To avoid this problem, set V6Display to YES to specify that you are running Version 6 code.

You can also set a session attribute to control the run-time setting of the V6Display state. The attribute is V6DISPLAY and has a Boolean value. Setting this attribute has the same effect as specifying the setting at startup. However, you must hide all existing windows.

When you set the V6Display option or session attribute:

The character unit height is recalculated to the height of the font specified by the DefaultV6UpdateFont option.
The character unit width is recalculated to the width of an average character in the font specified by the DefaultV6UpdateFont option.
The default font is automatically changed to use the font specified by the DefaultFixedFont option.
All OpenEdge fill-ins are created without a border.
OpenEdge fill-ins keep any trailing spaces.
All OpenEdge fill-ins that are enabled for update use the font specified by the DefaultV6UpdateFont option (by default, the default fixed font with underlines). This means that updateable fill-ins are drawn with underlines.
Frame titles are drawn so that the frame title height measures exactly one character unit.

The V6Display option or attribute does not enable support for PUT SCREEN. In addition, if you set the V6Display option, Version 7 applications that have not been compiled with the V6Display option set to YES will draw screens incorrectly.

Note: The V6Display option is intended for use with applications, not with the OpenEdge ADE. The ADE is not supported when V6Display is set to YES.

If you plan to use Version 6 user interface code with Version 7 tools (or your own Version 7 interface), Progress Software recommends that you use the V6Frame option instead of V6Display.

V6FontNumber

V6FontNumber=n

Lets you specify the font for Version 6 frames.

By default, this option points to the font defined as font3 in the [Fonts] section. Font3 is the ADE character-mode font. If you change the V6FontNumber value, make sure you define the new font number in the [Fonts] section.

Note: Do not change the definition of font3 in the [Fonts] section. OpenEdge relies on that font definition for other purposes.

V6FrameBGC

V6FrameBGC=n

Lets you specify the default background color for all frames that use the V6FRAME option. Valid settings include any number that corresponds to a color in the OpenEdge color table.

WindowSystem

WindowSystem=character-string

Lets you specify the value used by the WINDOW-SYSTEM preprocessor directive. Valid settings include any character string.

Colors section

The Colors section of the progress.ini file contains options that specify the colors that make up the color table for use with graphical user interface clients. There are 16 colors available to an application for use as either foreground or background colors. You can specify up to 256 colors.

Note: Do not change the first 16 colors. These colors are reserved for the Application Development Environment (ADE) tools. Changing them could cause the OpenEdge ADE tools to malfunction.

Each entry in the Colors section performs two semantic functions: it defines a color, and it maps that color to an integer in the range 0 to 255. An application specifies this integer when making a color assignment to a widget.

Specify a color entry using the following syntax:

colorn = { R , G , B , | colorname }

n

An integer from 0 to 255 that specifies the color table entry.

R

An integer that specifies the amount of red present in the color.

G

An integer that specifies the amount of green present in the color.

B

An integer that specifies the amount of blue present in the color.

colorname

Any of the following color names, mapped to the colors defined in the Windows Control Panel:

COLOR-SCROLLBAR COLOR-BACKGROUND COLOR-ACTIVECAPTION COLOR-INACTIVECAPTION COLOR-INACTIVECAPTIONTEXT COLOR-MENU COLOR-WINDOW COLOR-WINDOWFRAME COLOR-MENUTEXT COLOR-WINDOWTEXT COLOR-CAPTIONTEXT COLOR-ACTIVEBORDER COLOR-INACTIVEBORDER COLOR-APPWORKSPACE COLOR-HIGHLIGHT COLOR-HIGHLIGHTTEXT COLOR-BTNFACE COLOR-BTNHIGHLIGHT COLOR-BTNSHADOW COLOR-GRAYTEXT COLOR-BTNTEXT

Any entries you add to the color table must be sequential. For example, since the installed progress.ini file defines color0 to color15, the next color you add must be color16. If you add an entry for color17, OpenEdge ignores it if color16 is undefined.

For backward compatibility, color0 to color15, as installed, are the same as the colors supported in Version 6. See the chapter about colors and fonts in OpenEdge Development: Programming Interfaces for a listing of these colors.

For backward compatibility, the progress.ini file specifies the following color pairs for Version 6 applications:

NORMAL specifies the colors for fill-ins that do not have input focus.
INPUT specifies the colors for fill-ins that have input focus.
MESSAGES specifies the colors for the message area.

NORMAL, INPUT, and MESSAGES each take a pair of integer values from 0 to 255. The integers represent color table entries. For example, in the default progress.ini file, NORMAL is defined as foreground equal to color table entry 0 (RGB value 0,0,0) and background equal to color table entry 15 (RGB value 255,255,255).

The following example shows how to redefine NORMAL as foreground equal to color table entry 3 and background equal to color table entry 12:

NORMAL=3,12

Default Window section

The Default Window section of the progress.ini file specifies the following options for a graphical user interface client’s default window:

The location; specify the location as an x,y pixel value.
The size; specify the size as a number of rows and columns. The default size is 25 by 80.

Following is a sample Default Window section:

[Default Window] x= y= rows= columns=

Fonts section

The progress.ini file as installed contains font table entries for the OpenEdge ADE tools. OpenEdge uses the default system fonts defined in the Startup section, unless you add additional fonts to the existing font table in the Fonts section.

Note: You can add site-specific fonts to the file. Do not change the first 8 fonts. These fonts are reserved for the Application Development Environment (ADE) tools. Changing them could cause the OpenEdge ADE tools to malfunction.

Determine which screen fonts exist in your environment. The fonts you choose should be graphically compatible. One way to choose fonts is to use the font common dialog box.

The font table can contain up to 256 entries. Each entry in the table performs two semantic functions: it names a font that exists in your environment and it maps that font to an integer from 0 to 255. An application specifies this integer when making a font assignment to a widget.

Note: You cannot enter extra spaces in the font definition section. Extra spaces will cause the error 4499.

Specify a font entry using the following syntax:

fontn=typeface, [ size point-size, keyword, ... ], [ script=scriptname ]

n

An integer that specifies the font table entry.

typeface

A valid typeface name, such as Times or Courier.

point-size

The size of the font, in points. If you omit the point size, OpenEdge uses the default point size as defined by the typeface.

keyword

You can specify the following keywords: bold, italic, underline, or strikeout.

scriptname

By default, OpenEdge uses the script (character set) of the Windows FixedSys font for all fonts specified in the environment. If you select a different script when editing a font using the font common dialog, OpenEdge writes the specified script name to the font entry.

WinChar Startup section

The WinChar Startup section of the progress.ini file contains options that specify the following environment characteristics for character clients:

Default interface attributes
Default key bindings

The WinChar Startup section also contains OpenEdge environment variables that you can set for use with character clients. See Table 4–5 in the "Specifying environment variables" section for a list of environment variables you can set in the WinChar Startup section.

The WinChar Startup section contains the following options:

BrowseRowMarker

BrowseRowMarker=n

Lets you specify a character to represent a browse row marker. Valid settings include any number that corresponds to a character in the CPSTREAM character set.

CursorHeight

CursorHeight=n

Lets you specify the height of a cursor as a percentage. Valid settings include any number between 0 and 100. This option overrides the UseDosCursor setting.

EnableMouse

EnableMouse={ YES | NO }

Set to YES to enable mouse input. Set to NO to disable mouse input. The default value is YES.

FastCursorMode

FastCursorMode={ YES | NO }

For WebSpeed agents, this option is set to YES by default so that the Progress 4GL client does not process the normal hiding and showing of the cursor during display. This is the default behavior for WebSpeed agents since WebSpeed applications do not have cursors (they do not have a console). This option setting improves the performance of WebSpeed applications.

For character clients, this option is set to NO by default. Using FastCursorMode=YES with the character client on Windows can cause incorrect cursor behavior so make sure you leave this option set to NO if you are not using WebSpeed.

Caution: To avoid possible performance issues and incorrect cursor behavior, do not change the default setting of this option until you first talk with a Progress Software Technical Support representative.

MenuMnemonicColor

MenuMnemonicColor=n

Lets you specify the color of mnemonic characters in menu items. Valid settings include any number that corresponds to a color in the OpenEdge color table.

SingleLineBorder

SingleLineBorder=n,n,n,n,n,n,n,n

Lets you specify the characters used to draw borders and lines (such as frame borders, rectangles, submenu and pop-up menu borders, and horizontal and vertical lines). Valid settings include any eight numbers that correspond to characters in the CPSTREAM character set, separated by commas.

These eight numbers represent the corners and sides of a rectangle and must be specified in the following order: top, bottom, left, right, top-left corner, top-right corner, bottom-right corner, and bottom-left corner.

SysCheckmark

SysCheckmark=n

Lets you specify a character to represent a selection marker in widgets (such as a selection list, menu, or browser). Valid settings include any number that corresponds to a character in the CPSTREAM character set.

UseDosCursor

UseDosCursor={ YES | NO }

Set to YES to change the cursor from an underscore to a solid block when switching from insert mode to over-strike mode in a fill-in field or editor widget. Set to NO to use an underscore as the cursor in either mode. The default value is NO.

V6Keys

V6Keys={ YES | NO }

Set to YES to use a set of key bindings that are Version 6 compatible by default. The default value is NO.

V6FKeys

V6FKeys={ YES | NO }

Set to YES to use the bindings for the CTRL, ALT, SHIFT, and F13 to F39 keys that are Version 6 compatible by default. The default value is NO.

WinChar Colors section

The WinChar Colors section of the progress.ini file contains options that specify the colors that make up the color table for use with character clients.

Each entry in the WinChar Colors section performs two semantic functions: it defines a color, and it maps that color to an entry in the color table by specifying an integer from 0 to 255. An application specifies this integer when making a color assignment to a widget.

Specify a color entry using the following syntax:

keyword | colorn = { [ BLINK- ] [ BRIGHT- ] fgnd-color | bgndcolor }

keyword | colorn

You can also specify color0, color1, and color2 using the NORMAL, INPUT, and MESSAGES keywords, respectively. The keyword overrides the colorn specification. That is, if you specify both colorn and its corresponding keyword, OpenEdge displays the colors you specified with the keyword.

fgnd-color

The color to use for the screen foreground.

bgnd-color

The color to use for the screen background.

For information about color definitions for the WinChar Colors section, see the Color Phrase reference entry in OpenEdge Development: Progress 4GL Reference .

WinChar Default Window section

The WinChar Default Window section of the progress.ini file specifies the line mode for a character client. You can specify 50 rows if your hardware supports 50-line mode. Specify 25 rows if you want the application to be compatible with Progress Version 6 or if you want to port the application to a character terminal.

The following is an example WinChar Default Window section:

[WinChar Default Window] rows=25

WinChar Keys section

The WinChar Keys section of the progress.ini file defines the customized key bindings for use with character clients. Table 4–2 lists the user-definable key bindings in the Windows environment. For a complete listing of the Windows key function and key label mappings for handling user input, see OpenEdge Development: Programming Interfaces .

Table 4–2: User-definable key bindings in Windows

Key function	Key label
APPEND-LINE	CTRL+A
BLOCK	CTRL+V
BREAK-LINE	CTRL+ALT+B
CLEAR	F8
COPY	F11
CUT	F10
DEFAULT-POP-UP	SHIFT+F4
DELETE-LINE	CTRL+D
END-ERROR	ESC
ENTER-MENUBAR	F3
FIND	CTRL+F
GET	F5
GO	F1
HELP	F2
INSERT-MODE	INS
NEW-LINE	CTRL+N
NEXT-FRAME	CTRL+TAB
PASTE	F12
PREV-FRAME	CTRL+SHIFT+TAB
PUT	F6
RECALL	F7

Specify a key-binding entry using the following syntax:

keyfunction=keylabel [ , keylabel ]

Use a single entry to specify a key binding; additional entries for the same key function are ignored.

If you specify more than one key label, OpenEdge uses the first when it needs to display a key label given a key function, as in “Enter data or press Escape to end.”

For example, the following entry maps the Help key function to the F2 key label, and the Go key function to the F1 key label:

HELP=F2 GO=F1

You can use any combination of CTRL, SHIFT, and ALT keys. However, SHIFT only has an effect when used with ASCII keys. If an entry contains nonexistent key labels, the entry is ignored.

Note: Set the V6Keys option in the [WinChar Startup] section to enable OpenEdge to use a set of key bindings that are Version 6 compatible by default.

Debug-Init section

Do not modify information in the Debug-Init section.

Debug-Macros section

The Debug-Macros section of the progress.ini file contains a list of parameters that define initial macros used by the Debugger. You can also define your own macros. For more information, see OpenEdge Development: Debugging and Troubleshooting .

Debug-Buttons section

The Debug-Buttons section of the progress.ini file contains a list of parameters that define initial buttons used by the Debugger. You can also define your own buttons. For more information, see OpenEdge Development: Debugging and Troubleshooting .

Keys section

The Keys section is an optional section you can create in the progress.ini file to customize key bindings for the Windows environment.

Table 4–3 lists the static key bindings in the Windows environment.

Table 4–3: Static key bindings in Windows

Key function	Key label
BACKSPACE	BACKSPACE
BACK-TAB	SHIFT+TAB
CURSOR-DOWN	CURSOR+DOWN
CURSOR-LEFT	CURSOR+LEFT
CURSOR-RIGHT	CURSOR+RIGHT
CURSOR-UP	CURSOR+UP
DELETE-CHARACTER	DEL
END	END
HOME	HOME
PAGE-DOWN	PAGE-DOWN
PAGE-UP	PAGE-UP
RETURN	ENTER
TAB	TAB

Table 4–4 lists the user-definable key bindings in the Windows environment.

Table 4–4: User-definable key bindings in Windows

Key function	Key label
APPEND-LINE	No default
BLOCK	No default
BREAK-LINE	No default
CLEAR	No default
DEFAULT-POP-UP	F4
DELETE-LINE	No default
END-ERROR	ESC
FIND	No default
GET	No default
GO	F2
HELP	F1
INSERT-MODE	INS
NEW-LINE	No default
NEXT-FRAME	F6
PREV-FRAME	SHIFT+F6
PUT	No default
RECALL	No default

Keymap section

The Keymap section is an optional section you can create in the progress.ini file to define mappings between standard ASCII (7-bit) characters and extended (8-bit) characters. Extended characters are typically non-English alphabetical characters. OpenEdge uses these keymap entries to build a translation table for processing characters in the input and output streams.

Note: Using the Keymap section is the Version 6 technique for mapping characters. Using conversion tables is a better technique for processing characters. For information about defining conversion tables, see OpenEdge Development: Internationalizing Applications .

Use the IN statement, in a keymap entry, to map an ASCII character to an extended character using the following syntax:

[ MAP-language ] :IN(\ascii-char)=\extended-char:

language

An identifier that appears with the MAP option.

ascii-char

The 7-bit character, in octal (\nnn) format. You must specify all three digits.

extended-char

The 8-bit character, in octal (\nnn) format. You must specify all three digits.

Use the OUT statement, in a keymap entry, to map an extended character to an ASCII character using the following syntax:

[ MAP-language ] :OUT(\extended-char)=\ascii-char:

You can use multiple IN and OUT statements in a single keymap entry.

If you use extended character sets, you must specify character mappings for each character set on a per-terminal basis. For example, the following code fragment demonstrates how to map characters to German language characters:

[MAP-german] :IN(\102)=\341: :IN(\101)=\216: :IN(\141)=\204: :IN(\117)=\231: :IN(\157)=\224: :IN(\125)=\232: :IN(\165)=\201:

The IN statements in the preceding example map ASCII characters (B, A, a, O, o, U, and u) to German characters (ß, Ä, ä, Ö, ö, Ü, and ü). When OpenEdge sees the character A (\101) on input, it converts the character to Ä (\216). Likewise, when OpenEdge needs to send an Ä to the terminal, it sends [ (\101). The terminal sees A and displays Ä.

Suppose the terminal cannot display an Ä. You can use the OUT statement to specify an appropriate character to display for Ä, such as capital A. For example:

[MAP-german] :OUT(\216)=\101:

You can also specify keymap entries for the input and output streams using the MAP option with each of the following OpenEdge language elements:

INPUT FROM statement.
INPUT THROUGH statement.
INPUT-OUTPUT THROUGH statement.
OUTPUT THROUGH statement.
OUTPUT TO statement.

For more information about these language elements, see OpenEdge Development: Progress 4GL Reference .

Specifying environment variables

Table 4–5 lists the environment variables you can set in either the Startup section or WinChar Startup section of the progress.ini file.

Table 4–5: Environment variables

Variable	Description	Code example
PROPATH	A list of directory paths separated by commas. When you run a procedure from within an OpenEdge session with the RUN statement, OpenEdge searches for it in the directory paths defined in PROPATH in the order listed. Note: When OpenEdge encounters a period in PROPATH (“.,C . . .”), it substitutes the pathname of the current directory.	PROPATH=.,C:\Progress\ OpenEdge
PROMSGS	The full pathname of the OpenEdge error messages file. The default value is install-dir\PROMSGS. You only have to set the PROMSGS environment variable if you want to use an error messages file different from the default PROMSGS file in the installation directory.	PROMSGS= C:\Progress\OpenEdge\PROLANG \GER\PROMSGS.GER
PROCFG	The path name of your product’s configuration file. The configuration file is a data file that identifies the OpenEdge product and components that you are licensed to use. Reset PROCFG if you have moved the configuration file from the directory in which you installed OpenEdge.	PROCFG=C:\Progress\OpenEdge\ PROGRESS.CFG
PROSTARTUP	The name of the OpenEdge startup parameter file. The default is startup.pf.	PROSTARTUP= C:\Progress\OpenEdge\startup .pf
DLC	The pathname of the directory in which you installed the OpenEdge system software.	DLC=C:\Progress\OpenEdge